Im running Windows 7 Enterprise x64. When I try and add a network printer from our Print Server here in the office I get the following message: Operation could not be completed (error 0x00000bc4). No printers were found. I have tried manually adding the printer by browsing the print servers share and clicking on the print. I have tried manually adding by providing the the full share name of a printer. All result in the same error message above. The fun part is everyone else in the office can use the print server just fine. Including my co-worker who is running Win7 Enterprise x64 bit as well. Yes we have x64 drivers installed on the print server, as well. Any ideas?

Hi Amazingracer, I had the same problem a short while ago. The reason was, that i had an incompatible/old driver installed. My solution was to uninstall the printers and than to reinstall the network printer. Ralf

Is the network in your office a domain or a simple workgroup? Have you tried to following method? 1. Click Start, click Control Panel and double click Devices and Printers. 2. Click Add a Printer. 3. Select "Add a local printer". 4. Select "Create a new port". Choose "Local Port" as the type of the port. 5. In the box "Enter a port name", type the address as the following format. \\<IP address of the host computer>\<The Share Name of the printer> Then click Next. 6. Select the correct driver in from the driver list. If the required driver is not present, click the “Windows Update” button. After the update finishes, search for the proper driver again. Also I suggest you verify if you have correct permission to access the printer.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

We are having the same problem, but on a 2008 R2 citrix server running xenapp6. Group policy fails to connect printers because it receives this error. None of the above methods for resolution are viable? Also, this only happens when connecting to a specific print server (64 bit)... I can connect other print servers fine... There are 9 other servers that can connect to printers on the print server this one cannot connect to. Any ideas?

Terry D, same problem here, 5 citrix server, 4 no problem, one nothing but this error

We have exactly the same problem on 3 servers: 2008R2, XenAPP6 and HP Universal printer drivers. Any idea?

Same thing here! 2 2008R2 with XenAPP 6 all patched one works the other does not. This is now critical. Anyone from Microsoft care to shed some light???

After some testing and generally messing about if I browse to the print server using \\ipaddress\ instead of the UNC path it works! Just to confirm if I browse using add printers or devices - (this uses UNC path) does nto work - displays the error 'Cannot connect no printer found' If I browse via Windows Explorer using servername - same result. If however I use the server's IP address I can connect and download the drivers. Great I now know that the UNC path name is causing this issue - I just do not know how to fix it! Any thoughts as all our printers and session printers are created using the UNC path name. Can anyone else help with this?

It took a full day with the good guys from Microsoft to troubleshoot and resolve. To ensure you have the same issue can you browse to the printer server where the printers are shared using an IP address only. i.e. \\10.100.1.x instead of \\printservername. If this works there is an issue within the registry relating to client side rendering. On Windows 2008 R2 you can offload the print rendering to the client. However with RDS you do not want the session to try and render on the server. The fix is to delete the following reg key and reboot the server. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers Please Note: Before making any changes to the registry please backup both the whole registry and the key you are about to delete. Also I am not responsible for any issues or damage that may arise. Once deleted reboot the server and that should be you ready to go! Let me know how you get on. This has had me scratching my head for weeks!! Regards Alasdair